post style to blog style #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Kyle Davis <[email protected]>
CEHENKLE
suggested changes
Feb 24, 2022
|
|
||
| 3. **The project will follow a "release train" model for minor-version releases, and a "tentpole" model for major-version releases.** | ||
| The team wants to produce minor-version releases on a "release-train" schedule: every six weeks a new release comes out, and it includes all the new features that are ready at the time of release. Having a set release schedule makes sure OpenSearch is releasing in a predictable way and prevents a backlog of unreleased changes. In contrast, major-version releases will take place when there is a critical mass of new features that would create incompatibilities, since that’s the only opportunity to release them. These are called "tentpole" features because getting one of these in might hold a release. If any of the tentpole changes runs into serious problems, a decision would need to be made to move the release or wait until the next major release for that change. | ||
|
|
There was a problem hiding this comment.
That passive voice in the last sentence raises more questions than it answers, I think?
If any of the tentpole changes runs into serious problems, the folks working on it will need to add a comment on their meta tracking issue with an alert. At that point we the folks working on the issue and I can decide whether to cut scope, remove the feature from the release, or move the release date depending on the type and severity of the problem.
There was a problem hiding this comment.
"folks" is weird I acknowledge, BTW. So if you have a better word feel free to swap it in (tent pole features can come from anywhere.
CEHENKLE
approved these changes
Feb 24, 2022
Signed-off-by: Kyle Davis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Kyle Davis [email protected]
Description
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.